feat: create "identity" field for Site and update endpoints accordingly #12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add two new API endpoints for site management: - /api/secure-site with POST, PUT, and DELETE operations for authenticated site management - /api/public-sites with GET operation to retrieve public sites list Regenerated schema.d.ts using make build-typescript to include TypeScript definitions for the new endpoints and their request/response types.
add mongoose schema to represent Site. includes support for required fields such as name, coordinates, status, address, and cell_id, as well as optional fields like color and boundary with validation.
- Add POST /api/secure-site to create new sites - Add PUT /api/secure-site to update existing sites - Add DELETE /api/secure-site to remove sites
Routes were missing leading slash causing 404 errors for /api/secure-site
Create /api/public-sites GET route that returns list of sites
Apply suggested changes from code review
Update public sites endpoint name to /api/sites
…changes to ensure compatability
- Create secure-site.test.ts to test all the functions in secure-site.ts with exhaustive cases - Update package.json to include an "npm run test" script to run tests - Change secure-site.ts to use event handlers for ease of testing
Collaborator
|
One thing, use a more descriptive branch name for each PR. This will help tell the work quickly :) |
johnnzhou
reviewed
Oct 31, 2025
johnnzhou
reviewed
Oct 31, 2025
Collaborator
|
Can you also briefly describe the new design in the comment section? |
Collaborator
|
Can you move this to the description section at the top? |
Collaborator
|
@ananyaa06 Can you resolve the conflicts? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The old version of the API used names to identify Sites, which isn't a particularly stable form of identification. So I added an additional field called "identity" and modified the endpoints to use that as the primary identifier of Sites instead of the "name" parameter. The user passes in all fields except for the identity, which is a UUID generated randomly by the backend.